保存量化模型时出现奇怪问题 · Issue #333 · PaddlePaddle/PaddleSlim · GitHub

您所在的位置:网站首页 gnu date 保存量化模型时出现奇怪问题 · Issue #333 · PaddlePaddle/PaddleSlim · GitHub

保存量化模型时出现奇怪问题 · Issue #333 · PaddlePaddle/PaddleSlim · GitHub

2023-03-30 11:25| 来源: 网络整理| 查看: 265

详细一点:

2020-06-04 10:03:41,861-INFO: convert config {'quantize_op_types': ['conv2d', 'depthwise_conv2d', 'mul'], 'for_tensorrt': False, 'is_full_quantize': False, 'weight_bits': 8, 'dtype': 'int8', 'not_quant_pattern': ['skip_quant'], 'moving_rate': 0.9, 'activation_bits': 8, 'window_size': 10000, 'weight_quantize_type': 'abs_max', 'activation_quantize_type': 'moving_average_abs_max'} W0604 10:03:41.863718 401 init.cc:209] Warning: PaddlePaddle catches a failure signal, it may not work properly W0604 10:03:41.863734 401 init.cc:211] You could check whether you killed PaddlePaddle thread/process accidentally or report the case to PaddlePaddle W0604 10:03:41.863752 401 init.cc:214] The detail failure signal is:

W0604 10:03:41.863757 401 init.cc:217] *** Aborted at 1591265021 (unix time) try "date -d @1591265021" if you are using GNU date *** W0604 10:03:41.864516 401 init.cc:217] PC: @ 0x0 (unknown) W0604 10:03:41.864639 401 init.cc:217] *** SIGSEGV (@0xfffffffcf0372c60) received by PID 401 (TID 0x7f9d14250700) from PID 18446744073444732000; stack trace: *** W0604 10:03:41.865288 401 init.cc:217] @ 0x7f9d13e2f390 (unknown) W0604 10:03:41.870870 401 init.cc:217] @ 0x7f9caa112069 paddle::framework::ProgramDesc::ProgramDesc() W0604 10:03:41.874686 401 init.cc:217] @ 0x7f9caca5ef10 paddle::framework::ir::Graph::Graph() W0604 10:03:41.876364 401 init.cc:217] @ 0x7f9caa07b5d3 ZZN8pybind1112cpp_function10initializeIZNS_6detail8initimpl11constructorIJRKN6paddle9framework11ProgramDescEEE7executeINS_6class_INS6_2ir5GraphEJSt10shared_ptrISE_EEEEJELi0EEEvRT_DpRKT0_EUlRNS2_16value_and_holderES9_E_vJSP_S9_EJNS_4nameENS_9is_methodENS_7siblingENS2_24is_new_style_constructorEEEEvOT_PFT0_DpT1_EDpRKT2_ENUlRNS2_13function_callEE1_4_FUNES17 W0604 10:03:41.878095 401 init.cc:217] @ 0x7f9ca9de9c31 pybind11::cpp_function::dispatcher() W0604 10:03:41.878233 401 init.cc:217] @ 0x4e1307 PyCFunction_Call W0604 10:03:41.878350 401 init.cc:217] @ 0x5c3bd7 PyObject_Call W0604 10:03:41.878482 401 init.cc:217] @ 0x4f08be (unknown) W0604 10:03:41.878589 401 init.cc:217] @ 0x5c3bd7 PyObject_Call W0604 10:03:41.878726 401 init.cc:217] @ 0x55fa59 (unknown) W0604 10:03:41.878859 401 init.cc:217] @ 0x579f4c (unknown) W0604 10:03:41.878962 401 init.cc:217] @ 0x5c3bd7 PyObject_Call W0604 10:03:41.879094 401 init.cc:217] @ 0x5354af PyEval_EvalFrameEx W0604 10:03:41.879226 401 init.cc:217] @ 0x539a13 (unknown) W0604 10:03:41.879354 401 init.cc:217] @ 0x5356a2 PyEval_EvalFrameEx W0604 10:03:41.879485 401 init.cc:217] @ 0x539a13 (unknown) W0604 10:03:41.879565 401 init.cc:217] @ 0x53a6cf PyEval_EvalCode W0604 10:03:41.879700 401 init.cc:217] @ 0x6292c2 (unknown) W0604 10:03:41.879817 401 init.cc:217] @ 0x62b76a PyRun_FileExFlags W0604 10:03:41.879889 401 init.cc:217] @ 0x62bf5c PyRun_SimpleFileExFlags W0604 10:03:41.880007 401 init.cc:217] @ 0x63d506 Py_Main W0604 10:03:41.880118 401 init.cc:217] @ 0x4cfd11 main W0604 10:03:41.880800 401 init.cc:217] @ 0x7f9d13a74830 __libc_start_main W0604 10:03:41.880897 401 init.cc:217] @ 0x5d36e9 _start W0604 10:03:41.881467 401 init.cc:217] @ 0x0 (unknown) Segmentation fault (core dumped)



【本文地址】


今日新闻


推荐新闻


CopyRight 2018-2019 办公设备维修网 版权所有 豫ICP备15022753号-3